[Vorherige]
[Nächste]
[Index]
comp.sys.apollo Apollo Frequently Asked Questions (FAQ) part [3/3]
- Subject: comp.sys.apollo Apollo Frequently Asked Questions (FAQ) part [3/3]
- From: ahn@wfu.edu (Dave Ahn)
- Date: 20 Dec 1994 21:43:17 GMT
- Newsgroups: comp.sys.apollo, comp.answers, news.answers
- Summary: This posting contains a list of Frequently Asked Questions and their answers about Apollo Domain series computers.
Archive-name: apollo-faq/part3
Archive-location: ftp://ftp.wfu.edu/usenet/apollo/FAQ
Posting-Frequency: monthly
Last-modified: Tue, 4 Oct 1994
Version: 5
Keywords: FAQ, Apollo, Domain/OS
------------------------------------------------------
[5.15] What are the specs of monitors once sold by HP/Apollo?
------------------------------------------------------
Russell Ayling (rayling@pandc.rta.oz.au) has assembled a file of information
from an HP source plus bits and pieces picked up here and there. The file is
rather long so it's available from:
ftp://ftp.wfu.edu/usenet/apollo/doc/monitor-info
--( 3/4/94, Dave Ahn <ahn@hbar.phy.wfu.edu> )
---------------------------------------
[5.16] How can I connect my Macs to my Apollo?
---------------------------------------
Carlton B. Hommel <notelrac@world.std.com> has written the file
"mac2apollo," which is available via anonymous ftp from:
ftp://ftp.wfu.edu/usenet/apollo/doc/mac2apollo.
--( 3/4/94, Dave Ahn <ahn@hbar.phy.wfu.edu> )
--------------------------------------------
[5.17] Can I use a non-Apollo monitor on my Apollo?
--------------------------------------------
Every multisync I've tried, to date, has worked on the Apollo's. Even if
the monitor does not have RGB BNC connectors, as long as it will support
sync on green, there is no real problem. I've been cutting up the Apollo
cables and wiring them up to both the 9 pin and 15 pin video connectors.
Just solder the red coax to the 'red drive' and the ground to 'red ground'
and so on. So far, everything has been working out real nice.
If you've got a multisync with the BNC connectors, there is usually
an option or switch to allow 'sync on green' and you'll
be able to use the Apollo cable.
Another good plug and play monitor that can be used on the color Apollo's
is the HP 98751. This is a 19" Sony monitor that is vastly superior to
the old Panasonic that Apollo sold. These monitors are going for about
$500 on the used market. This monitor has BNC connectors, so it is
possible to use the old Apollo cable, makes it 'plug and play'.
--( 9/21/94, Mike Thomas <thomasm@agcs.com> )--
[6.0] =============== SALVAGING OLD APOLLOS ===============
-----------------------------------------------------------
[6.1] Can I use an Apollo controller and monitor on a Windows PC?
How about under XFree86 and Linux/NetBSD?
-----------------------------------------------------------
The simple answer is: sort of. The problem lies with the fact that nearly
all the Apollo video cards were developed specifically for the Apollo,
not the PC. The Intel platform is byte-backwards relative to the Motorola
that the Apollo's have in them; consequentlly, most operations that you
perform on the card (put in a char, draw a line, etc) will have to be
byteswapped, resulting in extra cycles. Furthermore, the video adapters
are entirely bitmapped, meaning they don't understand ASCII characters.
Another problem is that the cards live in a large amount of shared memory
which makes them unusable as a second display, since they live in the same
place where your other display adapters would live. The 8 plane cards
can be jumpered to live elsewhere, but unfortunately that is right where
the BIOS lives. In addition, the cards wouldn't respond to the BIOS'
queries during boot time, so bootup would be done blindly.
It is possible to write a driver to use the video cards, but there are
a number of problems. Besides, the SVGA cards on the market are very
cheap and would outperform anything you could do with the Apollo cards.
Herb Peyerl has done some work in writing a Unix driver for these
cards, although he was not very successful. Please contact him for more
information.
[ Note: this entry is quite out of date; there have been recent info
which tells of using 1280x1024 mono cards in PC's. It is
my understanding that the 1280x1024 mono cards can be used under
Xfree86 (with Linux or NetBSD) using drivers written by Herb Peyrel and
Hamish Coleman. If you have any information about this, please let
me know so that I can include it in the FAQ. ]
The Apollo monitor, though, can be used with PC's provided...
A friend of mine took one of our old Apollo monitors and built a simple sync
circuit (consisting of a 74ls02 and a 4066 and a pot. ) for his ATI Ultra
card... It works fine in 1024x768 mode which is a bit of a problem if you
don't automatically bring up windows on boot or XFree86 or whatever graphics
system you're using... I'm in the process of doing a similar thing myself
and plan to have two monitors.. One Hercules for regular dos/unix work and
then my ATI Wonder/XL with this monitor for Windows/Xfree86...
I've tried the same circuit with the hi-res monitors (1280x1024) and
it works even better on those!
This diagram is available via anonymous FTP from:
ftp://ftp.wfu.edu/usenet/apollo/doc/monitor-sync.ps
or directly from the author:
Tony <tony@ajfcal.cuc.ab.ca>
Are there any uses for anything else from an Apollo?
The Case/Power supply can be adapted to hold a PC in a relatively easy
fashion.... If you have a desoldering machine; you may find a use for the
memory chips on the cards... If you had a Disk then it could be potentially
useful (either MFM or ESDI depending on the disk). The disk controllers are
not useful... The ethernet cards are simply 3c505's with an Apollo boot prom
which can be removed... The token ring cards are useless for non-apollo work
as far as I can tell...
--( 2/15/94, Herb Peyerl <hpeyerl@novatel.cuc.ab.ca> )
The 98751A is a Lo-res color, 1024 x 768, 47.7khz/60Hz. These monitors are
fixed frequency, 47.7khz~50.5khz. I don't know of any PC brand graphics
cards that support these monitors.
--( 3/25/94, Steven Gaudet <sjg@world.std.com> )--
I don't know much about VGA, but I thought that you just selected a pixel
clock from some small set of available clocks that usually run from 28 MHz
on up to 85 or so, then you could set the length of scan lines and sync
pulses to any number of pixel clocks. That would imply that you can use any
monitor at all, within limits, as long as you know the timings it will sync
to.
Exact timings are available in the monitor-info file in the apollo archives
at archive.umich.edu. The 1024x800 color monitor has a horizontal display
interval of about 15 usec, so that means a pixel clock around 70 MHz.
You would have to combine the sync somehow, since the Apollo monitors want
it composite with video on the green channel, and VGA supplies it
separately, but that should be easy to do with a few diodes and maybe a
transistor or two.
--( 3/25/94, Jim Rees <Jim.Rees@umich.edu> )--
I still have not succeeeded in finding a card supported by XFree86 that will
work with the Apollo 1280x1024 color monitors, but I did get some
information recently that might be of assistance to people (hopefully the
next version of XFree86 will be usable).
The 1280x1024x8 graphics card can be used in a PC with Windows 3.1.
Specifically, the Apollo card is a special version of the Matrox PG-1281
called the PG-1281/AP. I called Matrox and one of the technical folks
there told me that the standard PG-1281 Windows 3.1 drivers should work,
but it would need a special parameter file with the video parameters.
He created the files for me, and this morning I was able to get the card
and monitor running in a PC. I wouldn't say the card is particulary fast,
but it definitely does work as a second monitor for Windows on a PC that
has a monochrome display. If anyone else wants to do this, I'm sure I can
pass along the information and code, since the drivers were available for
public download.
--( 7/28/94, Leonard N. Zubkoff <lnz@dandelion.com> )--
[ Maintainer's note: The drivers are available by anonymous FTP from
ftp://archive.umich.edu under the file 'pg1281ap.zip' ]
>I'm attempting to run an Apollo color 1280x1024 monitor off my PC using
>XFree. I've got the hardware connection fairly stable, but am having
>problems with setting up an XFree video mode.
This monitor is a Matsushita J2P36X. To drive it at 1280x1024 you'll need
a dot clock of 125 MHz. If your VGA card won't do this, you may have to
tear into the monitor's sweep circuitry, since it's not a multi-sync design.
Here are the timing numbers you'll need for your Xconfig file. If you get
this to work, please send me your Xconfig.
Pixel rate - 124.996 MHz
Pixel period - 8.000256 nsec.
Aspect Ration 5/4
Horizontally displayed pixels - 1280
Vertically displayed lines - 1024
Horizontal frequency - 73.702 kHz
Horizontal period - 13.568 usec., pixels 1696
Horizontal front porch - 0.256 usec., pixels 32
Horizontal sync - 1.536 usec., pixels 192
Horizontal back porch - 1.536 usec., pixels 192
Horizontal blanking - 3.328 usec., pixels 416
Horizontal display area - 10.240 usec., pixels 1280
Vertical fields per frame (noninterlaced) - 1
Vertical field frequency - 68.24 Hz
Vertical field period - 68.24 msec, lines 1080
Vertical front porch - 40.7 usec, lines 3
Vertical sync - 40.7 usec, lines 3
Vertical back porch - 678 usec., lines 50
Vertical blanking - 759 usec, lines 56
Vertical display area - 13.893 msec, lines 1024
--( 9/19/94, Dan Waugh <dwaugh@bnr.ca>,
Jim Rees <Jim.Rees@umich.edu> )--
There are actually two versions of this monitor, one with a 68Hz vertical
refresh rate and the other with 70Hz. Here are Xconfig mode lines for both
of them (these have been tested with my STB Pegasus VL):
# Apollo 010700-005 1280x1024 Color Display
"1280x1024-68" 124.996 1280 1312 1504 1696 1024 1027 1030 1080
"1280x1024-70" 124.996 1280 1312 1472 1664 1024 1027 1030 1072
In order to use one of these monitors with XFree86, you'll need a graphics
card that supports the 125MHz pixel clock as well as providing RGB outputs
with sync-on-green.
--( 9/22/94, Leonard N. Zubkoff <lnz@dandelion.com> )--
----------------------------------------------------
[6.2] Can I connect an old ESDI drive to a SCSI interface?
----------------------------------------------------
There is a way to use ESDI drives with an SCSI interface (such as a PC
with an SCSI card or a Sun workstation).
It seems that Adaptec makes a translator which allows you to connect ESDI
drives to SCSI controllers.
--( 2/15/94, Willem Jan Withagen <wjw@ebh.eb.ele.tue.nl> )
I have an Emulex MD-21 which is the device you want. It is an ESDI to SCSI
converter. It controls both 10 and 15 mbit/sec drives and provides a SCSI-1
interface on the other side. The interface will handle two ESDI drives as
logical units 0 and 1. (Suns and NeXTs recognize the 2nd logical unit -
anyone know if apollos do?) I've had this board connected a wide range of
systems (NeXT, Sun, Mac, Apollo) without any problems. This board is a
discontinued item, but you can buy them from Sun resellers since they were
commonly used in Sun shoeboxes. I paid $40 for mine from such a vendor.
--( 2/15/94, David Lacey, M.D. <David-Lacey@uiowa.edu> )
----------------------------------
[6.3] Can I use old ESDI drives on PC's?
----------------------------------
I took a Maxtor 4380E disk drive out of one of our Apollo nodes, and am
trying to get it to work on a PC. However, I'm not having much succes.
It's a 386 running DOS 5, and an NCL 5355 disk controller. When I run debug
and low level format it, all seems well. It says the proper number of cyl,
heads and sectors, but when I run fdisk and format, it thinks its only a
52 MB drive.
I was able to get it to about 150 MB by playing with the CMOS settings, but
no higher. Using Norton Utilities, I modified the boot table to a higher
number of cylinders, and then fdisk saw 270 MB, but after formatting it, it
was unreadable by DOS.
Does anybody out there now how to get one of these disks too work on a PC?
--( 2/15/94, Steve Levesque <levesque@galaxy.mpr.ca> )
I have used the Maxtor-4380E on several PC's using both Everex and Adaptec
ESDI controllers. In both cases, I used debug to low level format the
drive (-g=c800:5) using the controller's onboard ROM format utility.
Since DOS has a limit of 1024 cylinders and the drive has 1222 cylinders,
when you run fdisk you only see about 270Mb of disk. (I don't know why you
are only getting 52Mb).
To use the full 122 cylinders, you need to use the low level format's
optional sector translation capability and run 63 sectors per track.
Actually, the controller fakes dos into thinking that there are fewer
cylinders but more sectors per track.
Using sector translation, my drives after being formatted with dos are
coming out to 321Mb. The 52Mb number is strange. Make sure that when you
low level format you are using cyl=1222, head=15, spt=36 and then after it
formats, do the sector translation to spt=63.
Maybe several of your heads are dead, in which case you should be seeing
millions of bad sector entries.......
--( 2/15/94, Tom Wowianko <wowianko@aa.ab.com> )
--------------------------------------------------------
[6.4] What can I do with an old SMS-Omti hard disk controller?
What about a WD7000V-ASE or a WD7000-ASC?
--------------------------------------------------------
Hi there. Someone out there must know how to jumper an Apollo disk
controller for use in a PC. I've tried several different ones, including
the SMS controllers and even a WD7000V-ASE with no luck. The floppy side
seems to work just fine... I even think that on one controller I got the
IO address space correct, but probably messed up on the DMA channels. I
don't know... if anybody out there can help me (Hey old Apollo employees,
you listening?) Ideally, of course, I'd like to be able to use the WD7000,
but if somebody can help me out using ANY of those controllers I'd really
appreciate it.
--( 6/3/93, Andrew F Gunnesch <afgun@engin.umich.edu> )
I've put some time looking into the SMS-OMTI controller. Our determination
was that you can't do it for much less than you could buy a new card of
equal intelligence. We tracked down SMS somewhere in California, and they
faxed us some manual pages on it, so that we could jumper it. The floppy
worked fine, but no hard drive. It turns out that there is a jumper to
disable the on-card BIOS, which Apollo does. It also turns out that since
they disable the BIOS, and they were buying lots of them, they got SMS to
remove the BIOS ROM. So now it has absolutely no smarts. If you can find a
driver, you may be able to get it to work. Otherwise, SMS charges $40 min
plus parts and time to make it back to a real card.
I suspect that you'll need a driver to make the WD7000 work in a PC also -
you may be able to buy one from Western Digital.
--( 6/3/93, Steve Swamp <swamp@bnr.ca> )
If you have a WD7000-ASC or WD7000-FASST2 (SCSI only) card pulled from an
Apollo, you can use it in a PC to control two floppies and two SCSI HD's
without any additional software or drivers if the Boot PROM is still
attached to the board. If you are missing the boot PROM or want to use
the controller with other SCSI devices, then you will have to get the
drivers and possibly a PROM and firmware upgrade from Columbia Data
Products. As of 7/26, a firmware upgrade (turns the card into SCSI2)
and PROM upgrade (v3.36 is latest) costs $10, and the full drivers and
documentation can be purchased for $85. In order to use the WD7000
under Windows 386 Enhanced mode, the PROM revision must be 3.36 (see
the README files under Windows 3.1). I have the jumper settings and
some helpful files if you want them. I'm still testing this configuration
out right now, but once I'm satisfied I will put detailed information in
this FAQ.
If you have a WD7000V-ASE, then I am not sure. It is my understanding
that the ASE is identical to an ASC, but with additional hardware to
support ESDI disks. If this is true, then you should be able to disable
the ESDI bus and set the SCSI jumpers properly and use it in a PC, if
you have the proper PROMs. If you have any experience with getting the
ASE to work in a PC, please let me know, and I'll add the information
to the files I have and make it available on this FAQ.
--( 7/26/94, Dave Ahn <ahn@hbar.phy.wfu.edu> )--
-------------------------------------------
[6.5] Can I convert my Apollo into an X-terminal?
-------------------------------------------
Basically, it is possible and relatively easy to convert an Apollo into
an X-terminal by using the standard Domain/OS software. All that is
required is to get the machine to boot straight into "Xdomain -query host."
The detailed information and procedure to do this is in a file written
by Dusan U. Baljevic available from:
ftp://ftp.wfu.edu/usenet/apollo/doc/apollo-as-xterm
--( 8/5/94, Russell Ayling <rayling@rta.oz.au> )--
----------------------------------------------------
[6.6] Can I run a different operating system (HPUX, BSD, etc) on my Apollo?
----------------------------------------------------
If you have an HP9000/400 series running Domain/OS, then you can switch
to HP-UX. I believe only up to HP-UX 9.x is officially supported on the
Motorola based HP's (9000/3xx, 4xx), but I could be wrong. The following
instructions should help you convert from Domain/OS to HPUX.
If you have the original Apollo Domain series workstations, then no.
There are no ports of public (or commercial) OS implementations to the
Apollo Domain platform. There is some work going on with the NetBSD
project team with porting a version of NetBSD to a Motorola based
platform (Amiga), but I've been told that this won't be completed any
time soon, if at all. BSD4.3 and 4.4 were actually designed on HP
9000/3xx's, which are Motorola based boxes running HP-UX, so there is
some groundwork already done there, but unless you have the knowledge,
time, effort and the license/access to the source code, porting BSD4.3/4.4
or any other operating system is probably not an obtainable alternative
to Domain/OS.
Besides, as every Apollo fanatic would ask, "why would you want to?"
Domain/OS already supports BSD4.3 and SV3 programming and user
environments in addition to Apollo's Aegis. With a little tweaking and
adjusting, you can make your Domain/OS "feel" and "act" like a BSD4.3
system.
--(7/26/94, Dave Ahn <ahn@hbar.phy.wfu.edu> )--
Actually, you'll be surprised how well your hardware configuration will run
HPUX. We've even converted 400t with 16MB of memory into HPUX boxes and get
quite some mileage out of them. Depending on the mix of applications you'll
be running, a 425t with 32MB of memory may in some case be as responsive in
HP-Vue as a 715 with the same amount of memory, i.e s700 needs lots of
memory to perform well.
With all that said, the only reason I'd convert to HPUX is for 3rd-party
application support. However, the latest HPUX for s400 (series 400), 9.03,
may also be the last release. 3rd-party application support for HPUX on
the S400 platform is going down the same road as Domain.
Here're some of my experiences with converting s400 to run HPUX:
1. Keyboard and mouse will need to be replaced (~ $100.00). PC-AT style
keyboard is highly recommended.
2. To switch the bootprom from Domain to HPUX mode:
a. At the Mnemonic Debugger prompt, type:
> CF
b. Select option 2 (Boot mode)
c. Select option 2 (HP-UX compatible)
d. Select option to execute and make the selected configuration
permanent.
3. Root swap space must be at least the size of physical RAM. Twice the
size of RAM is recommended. Further down the road, if some
application requires more swap space, use file swap.
4. Depending on the application mix you'll be running, you may have to
tune the kernel to increase some system parameters.
5. If you want to use the serial port, you'll have to regenerate a new
HPUX kernel with the serial driver (apci) included.
6. If you've more than one system to convert, you can load HPUX and build
a source area on the 1st system from physical media, and install the
rest of the systems across the network using /etc/update and
/etc/netdist.
7. In general, it takes a lot more time to administer a network of HPUX
boxes than Domain boxes.
--( 7/26/94, Hung Do <do@dolabela.css.beckman.com> )--
--------------------------------------------------
[6.7] Can I use the Apollo keyboard on another computer?
--------------------------------------------------
> Has anyone possibly gotten a connector/adaptor to connect an Apollo
> keyboard to a Sun station, or a workaround (do-it-yourself)?
--( 7/28/94, David Stonehouse <dstone@xpress.MITRE.org> )--
If I remember right, the Apollo's keyboard is connected to an sio serial
port (/dev/sio), so it's a bit RS232-like. The connector's pin assignments
are:
CPU end of cable:
U 1 - +8.5 Vdc (see below) Red wire
6o 7o 2 - Data to CPU (TXD) Yellow wire
3 - Logic ground Green wire
1o 3o 4 - RESET Orange wire
8o 5 - Data to keyboard (RXD) Grey wire
4o 5o 6 - Not used
2o 7 - Logic ground Blue wire
8 - Not used
SHIELD - Chassis ground
Keyboard end of cable:
5o 4o 3o 2o 1o
9o 8o 7o 6o
2 - +8.5 Vdc (DN3000/3500) or +12 Vdc (DN4000/4500/3550)
4 - Data to CPU (TXD)
6 - Logic ground
3 - RESET
5 - Data to keyboard (RXD)
1 - Not used
7 - Logic ground
8 - Not used
9 - Not used
SHIELD - Chassis ground
--( 7/28/94, Dan Bennet <dan@hpwina39.uksr.hp.com> )--
[7.0] =============== THIRD-PARTY VENDORS ===============
-------------------------------------------------
[7.1] Is there a list of third-party component vendors?
-------------------------------------------------
Additions/deletions to this list and comments about the vendors (good? new
stock? still in business?) should be sent to David Ahn
<ahn@hbar.phy.wfu.edu>.
National Peripherals, Inc North Central Peripherals
1111 Pasquinelli Drive, Suite 400 14041 Burnhaven Drive, Suite 114
Westmont, IL 60559 Burnsville, MN 55337
(312) 325-4151 (612) 881-2302
==> DNxxxx memory ==> DNxxxx memory
==> 9000/400 series memory? ==> 9000/400 series memory
==> Maxtor 8760E (697MB) drives ==> Maxtor 8760E (697MB) disk drives
==> SCSI drives for 9000/400's ==> Exabyte 8mm tape drives
==> Exabyte 8mm tape drives ==> other disk drives, etc.
==> other disk drives, etc.
AnDATAco Computer Peripherals Infotek Systems
9550 Waples Street 1045 S. East Street
San Diego, CA 92121 Anaheim, CA 92805
(619) 453-9191 (714) 956-9300
==> DNxxxx memory ==> 9000/400 series memory
==> Maxtor 8760E (697MB) drives
==> Exabyte 8mm tape drives
==> other disk drives, etc.
Martech Digital Micronics, Inc
1151 West Valley Boulevard 5674 El Camino Real, Suite P
Alhambra, CA 91803 Carlsbad, CA 92008
(818) 281-3555 (619) 931-8554
==> 9000/400 series memory ==> 9000/400 series memory
R Squared MDL Corporation
11211 E. Arapahoe Road, Suite 200 15301 NE 90th St., Redmond, WA 98052
Englewood, CO 80112 (206) 861-6700 (206) 861-6767 FAX
(800) 777-3478 ==> memory, disk drives (internal,
==> DNxxxx memory? ==> external, removable, ESDI, SCSI,
==> 9000/400 series memory ==> winchester,floppy), optical (CDROM
==> 9000/700 series memory ==> erasable optical), tape & optical
==> SCSI drives for 9000/400 series ==> jukeboxes, tape drives (1/4", 4mm,
==> SCSI drives for 9000/700 series ==> 8mm, 1/2", 3480) for DN3000 &
==> other disk drives, etc. ==> up, and for HP 9000/300's,
==> /400's, /700's and /800's.
Mesa Tech ==> MDL also offers the same stuff
267 Boston Rd.; Suite 13 ==> for other platforms, such as Sun,
Billerica, MA 01862 ==> SGI, DEC, IBM RS-6000, etc.
ATN: Michael Hall
508-663-8254
MESA Tech: corporate office
9720 Patuxent Woods Drive
Columbia, Maryland 21046
301-290-8150
==> HP SCSI drives for 9000/400's
==> Exabyte 8mm tape drives
==> other disk drives, etc.
-------------------------------------------------
[7.2] Are there third-party vendors of ethernet boards?
Where can I get an ethernet card for my Apollo?
-------------------------------------------------
The ethernet board used in the Otter (dn3000 series) is a 3Com 505. You
can buy your own and perhaps save some money. If you buy the board from
Apollo, it comes with a special PROM, which you won't have if you buy direct
from 3Com. That means you won't be able to boot diskless over the ethernet,
or make remote dumps over the ether. But you'll still be able to boot from
disk, or over the ring if you have one. And once the node is booted,
everything else will work fine.
The 505 is more expensive than some boards, because it has quite a bit of
on-board smarts and buffering. No other ethernet board will work in the
Otter, unless you want to write your own driver, and even then you will lose
the ability to run domain protocols and TCP over the ether, which makes it
pretty useless.
Switch settings for the 505 are given in the file ether-switches, available
via anonymous FTP from:
ftp://ftp.wfu.edu/usenet/apollo/doc/ether-switches
--( 2/15/94, Jim Rees <Jim.Rees@umich.edu> )
I bought a 3C505 board from 3Com instead of Apollo because I'm not
interested in doing diskless booting over the ethernet. I know it's missing
a prom for doing that. I've set the jumpers as described in the
/systest/ssr_util/jumpers program with no luck.
--( 2/15/94, Bryan Province <bep@quintro.uucp> )
Correct settings are port 300, mem addr 80000, dma 6, intr 10, test mode
off, rom select off. If Domain/OS (and DEX) can't find the board at all,
you've probably got the port wrong. You should have jumpers 8 and 9 in,
where "in" is away from the back panel bnc and aui connectors.
A second board would go at port 310, mem addr 84000, dma 3, intr 9.
--( 2/15/94, Jim Rees <Jim.Rees@umich.edu> )
Correct, however all the original poster said was that self tests couldn't
find the board. I'm assuming that he's referring to the self tests that
run when powering up in normal mode (or when the appropriate prom command
is it "te" ?) is entered. If this is the ONLY time the board can't be
found, it's because of the lack of the boot prom (self test code is stored
in there). Run "ex config" and remove it's knowledge of the ethernet board
so it won't try to test it. The OS should find it ok (and nothing was said
in the original mail about whether the OS could or could not find it, I
assume that it could (it should!) ).
--( 2/15/94, Carl Heinzl <carl@Cayman.COM> )
--------------------------------------
[7.3] Where can I go besides HP for repairs?
--------------------------------------
I can recommend AMC Computer Services, Inc., 146-B Rangeway Rd., N.
Billerica, MA., 01862. Phone: (508)670-9395. They're a group of former
Apollo employees who have formed their own depot repair facility for Apollo.
They seem to possess considerable expertise and all of our experiences so
far have been very positive.
--( 2/15/94, Mike Thomas <honeywel@chama.eece.unm.edu> )
[8.0] =============== MISCELLANY ===============
-------------------------------------------------------
[8.1] What are the internal names for the various node types?
-------------------------------------------------------
DN100/400/420/600 <no name> (sau1)
DN300/320/330 Swallow (sau2)
DSP80/90 Sparrow (sau3)
DN460/660 Tern (sau4)
DN550/560 Stingray (sau5)
DN570/580/590-T Banshee (sau6)
DN3500 Cougar II (sau7)
DN4000 Mink (sau7)
DN4500 Roadrunner (sau7)
DN3000 Otter (sau8)
DN2500 Frodo (sau9)
DN10000 AT (sau10)
400s Trailways (030: sau12, 040: sau11)
400t Strider (030: sau12, 040: sau11)
400e Woody (sau11)
DN5500 Leopard (sau14)
--( 2/15/94, Nat Mishkin <mishkin@apollo.hp.com> )
-------------------------------------------
[8.2] Any funny Status codes and background info?
-------------------------------------------
% stcode 1D01001E Vendor "Apollo" can not be deleted (network license
server/server)
How about 13010008: trait not supported for wicked far-away objects (object
based systems/trait manager)
My favorite is still 220009: unit will not fit thru 25" hatch
(OS/magtape manager)
This refers to a large computer manufacturer (former employer of some of the
Apollo OS folks) that once bid on a government contract to supply computing
equipment for use on board submarines. They lost the contract when the
government discovered that the tape drive would not fit through the 25 inch
hatch used to load equipment onto a submarine. Anything that won't fit
through the hatch has to be loaded by cutting a hole in the hull.
--( 2/15/94 )
******************************************************************************
--[ Contributors ]--
Morgan Ryan of Neil Paterson Publishers was co-maintainer of this FAQ from
February 7, 1994 to July 28, 1994. Many thanks to him for his time and
effort, particularly in reformatting this FAQ.
Willem Jan Withagen of Eindhoven University of Techonology, The Netherlands,
was the maintainer of this FAQ from March 25, 1992 to February 7, 1994. The
effort Willem put forth to provide this service to Apollo users has been
invaluable and is greatly appreciated!
Jim Rees <Jim.Rees@umich.edu> of University of Michigan was the
maintainer of this FAQ before Willem Jan Withagen, and he continues to
make significant contributions with his help and knowledge.
Each question is accompanied by a list of people who have helped with the
answer. We've also dated each Q&A to reflect the last time it was updated.
If you have contributed but feel left out or know of someone else who has
contributed, please bounce us a piece of mail so that we may give proper
credits.
******************************************************************************
End of Apollo FAQ
--
Dave Ahn Internet: ahn@hbar.phy.wfu.edu, ahn@wfu.edu
#include <stdisclaimer.h>
"When you were born you cried, and the world rejoiced. Try to live your life
so that when you die you will rejoice, and the world will cry." -1/2 jj^2